To ensure that an application specified in a Web browser cannot cause an attachment to a non-JADE environment, you must specify the name of the Web application to which users can connect, by defining a unique [application‑name] section for each Web‑enabled JADE application.
IIS attempts to attach only to the applications whose names are specified as section names in the jadehttp.ini file.
The jadehttp library module can handle connections for up to 50 different hosts (that is, you can define up to 50 unique TcpPort[n], MinInUse[n], MaxInUse[n], TcpConnection[n], CloseDelay[n], and ConnectionGroup[n] parameters within each [application‑name] section).
The [application-name] section of the jadehttp.ini file contains parameters that define TCP/IP connections that are used instead of the default named pipe connections. For more details and the application requirements for TCP/IP connections, see "Connecting to JADE Applications from Internet Information Server (IIS)", earlier in this chapter.
To specify that TCP/IP connections are used to connect to JADE release 7.1 applications from IIS, you must define a section with a unique name within the jadehttp.ini file for each application, with the ApplicationType parameter and unique multiple TcpPort[n], MinInUse[n], MaxInUse[n], TcpConnection[n], CloseDelay[n], and ConnectionGroup[n] parameters within each [application-name] section. Set the ApplicationType parameter in each [application-name] section to RestServices, WebEnabledForms, WebServices, or HtmlDocuments.
The [application-name] section can contain the following parameters.